Repository navigation
One QUIC connection per endpoint-pair - #492
Merged
Merged
Conversation
LaurentRDC
commented
Oct 2, 2026
LaurentRDC
force-pushed
the
quic-multiplex-streams
branch
5 times, most recently
from
October 6, 2026 12:57
f051108 to
91a2799
Compare
LaurentRDC
force-pushed
the
quic-multiplex-streams
branch
from
October 6, 2026 13:03
91a2799 to
48aabee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR mimics the design of
network-transport-tcp, where everyEndPoint <-> EndPointpair. New connections are therefore QUIC streams instead, which takes advantage of QUIC's lack of head-of-line blocking.This change improves performance for dense network topologies. In particular, for multiple logical connections between two
EndPoints,network-transport-quicgoes from having 2x throughput overnetwork-transport-tcpto having 3x throughput